-
Notifications
You must be signed in to change notification settings - Fork 82
dataaccess functionality #384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
code/gateway/dataaccess.q
Outdated
| // Use upserting logic to determine behaviour | ||
| options::default,o; | ||
| if[`ordering in key o;options[`ordering]: go each options`ordering]; | ||
| o::adjustqueries[o;partdict o]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are o and options global variables? Can't the pre-processing funtion just return a result?
code/gateway/kxdash.q
Outdated
| @@ -1,6 +1,5 @@ | |||
| \c 200 2000 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't think we want this
code/gateway/kxdash.q
Outdated
| } | ||
|
|
||
| //Define the current .z.ps as a new function to be called in dashps | ||
| .z.ops:@[.:;`.z.ps;{.:}]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't use .z name space for custom functions
Also I think that should be value rather than .:
|
@robertcoen can you squash and merge this if it's good to go? |
Allow dataaccess queries to be executed from kx dashboards and also maintain TorQ's .z.ps functionality for queries made from kx dashboards.